Systems and methods for identifying a service qualification of a unit in a multi-unit building

ABSTRACT

A service qualification platform may receive, from a user device, a service request to qualify a unit of a multi-unit building to receive a service. The service qualification platform may obtain a service coverage mapping associated with the multi-unit building and may provide, to the user device and via a user interface that is associated with a geographic information system, a unit location request for an indication of a location of the unit within the multi-unit building. The service qualification platform may receive unit location information that is associated with the indication and may determine a service qualification metric based on the service coverage mapping and the unit location information, wherein the service qualification metric is associated with a capability of receiving the service within the unit. The service qualification platform may perform an action associated with the service qualification metric.

BACKGROUND

A network service (e.g., Internet access) may be provided via a wirelessnetwork (e.g., a fifth generation (5G) wireless network) to a customerresiding in a home, to multiple customers residing in units (e.g.,apartments, condominiums, and/or the like) of a multi-unit building,and/or the like.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1E are diagrams of one or more example implementationsdescribed herein.

FIGS. 2A-2B are diagrams of one or more example implementations relatedto determining a service qualification metric described herein.

FIG. 3 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 4 is a diagram of example components of one or more devices of FIG.3.

FIG. 5 is a flow chart of an example process relating to identifying aservice qualification of a unit in a multi-unit building.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

5G Ultra Wide Band service is a wireless network service that connects acustomer's home with ultra-wide band Internet. Unlike signals used for3G and 4G radio communication, 5G Ultra Wide Band signals aretransmitted via a precise pattern that does not propagate throughoutbuilding structures. As a result, knowing where the signals interactwith a multi-unit building and then precisely where any particular unitis within the multi-unit building is critical to understanding whether acustomer can receive and use a 5G Ultra Wide Band service.

Currently, if a customer who lives in an apartment unit or a condominiumunit desires such network service, the customer provides, to a networkprovider, a street address of the apartment complex or the condominiumcomplex. The network provider qualifies the apartment unit orcondominium unit for the network service based on a general availabilityof the network service at the street address. However, a specificapartment unit, condominium unit, a floor number, and/or the like maynot be qualified for the network service because of geographicalconstraints such as having windows that face a side of the buildingwithout coverage, or the like. This causes false positives indicatingnetwork coverage for the network service where there is no coverage.Thus, current techniques waste computing resources (e.g., processingresources, memory resources, communication resources, and/or the like),networking resources, human resources, and/or the like by incorrectlyqualifying wireless network coverage for a network service, correctingthe wireless network coverage for the network service, handling customercomplaints associated with the network service, and/or the like.

Some implementations described herein overcome a lack of a data sourcefor location information concerning units within a multi-unit building.Further, some implementations are able to calculate an existence orstrength of a signal (e.g., of a 5G signal) at a perimeter associatedwith a unit of the multi-unit building (e.g., at a building level,perimeter level, elevation level, and/or unit level).

Some implementations described herein provide a service qualificationplatform that qualifies a unit of a multi-unit building to receive anetwork service. In some implementations, the service qualificationplatform may receive, from a user device, a service request to qualifythe unit of the multi-unit building to receive the network service. Theservice qualification platform may obtain a service coverage mappingassociated with the multi-unit building and may provide, to the userdevice and via a user interface that is associated with a geographicinformation system, a unit location request for an indication of alocation of the unit within the multi-unit building. The servicequalification platform may receive unit location information that isassociated with the indication and may determine a service qualificationmetric based on the service coverage mapping and the unit locationinformation, wherein the service qualification metric is associated witha capability of receiving the network service within the unit. In someimplementations, the service qualification platform may perform anaction associated with the service qualification metric, such asprovide, based on the service qualification metric, a notification tothe user device that identifies whether the unit is capability ofreceiving the network service.

In this way, the service qualification platform identifies a servicequalification of a unit in a multi-unit building. Thus, the servicequalification platform reduces time required to qualify a networkservice for a unit of a multi-unit building, and conserves computingresources, networking resources, human resources, and/or the like thatwould otherwise be wasted incorrectly qualifying wireless networkcoverage for a network service, correcting the wireless network coveragefor the network service, handling customer complaints associated withthe network service, and/or the like.

FIGS. 1A-1E are diagrams of one or more example implementations 100described herein. As shown in FIG. 1A, a user device 105 may beassociated with a user (e.g., a technician) and a service qualificationplatform 110. In some implementations, user device 105 may include amobile device, a computer, a telephone, and/or the like that the usermay utilize to provide information to and/or receive information fromservice qualification platform 110. Service qualification platform 110may include a platform that determines whether a service is availablefor a unit of a multi-unit building. The service may include, forexample, establishing a local area network via an ultrawide bandwireless network (e.g., for a user of the unit of the multi-unitbuilding). Although implementations are described herein in connectionwith a multi-unit building, the implementations may also be utilizedwith a complex of multiple buildings.

As shown in FIG. 1A, and by reference number 115, user device 105 mayprovide a service request to service qualification platform 110. Forexample, the user of user device 105 may interact with an inputinterface of user device 105 to cause user device 105 to generate andsend the service request to service qualification platform 110. Theservice request may be associated with qualifying a unit of a multi-unitbuilding (shown in FIG. 1A as building A) to receive a service (e.g.,establishment of a local area network, via an ultrawide band wirelessnetwork, for the unit).

The service request may include building location information of themulti-unit building. The building location information may include astreet address of the multi-unit building, geographical coordinates ofthe multi-unit building, geographical coordinates of user device 105(e.g., when the user and user device 105 are located at the unit and/orthe multi-unit building), and/or the like. In some implementations, theservice request may include a unit identifier associated with the unitof the multi-unit building (e.g., an apartment number associated withthe unit, a suite number associated with the unit, and/or the like),floor information associated with the unit of the multi-unit building(e.g., information identifying a quantity of floors associated with theunit, information identifying which floor(s) of the multi-unit buildingare associated with the unit, and/or the like), and/or the like.

In some implementations, the service qualification platform 110 may send(e.g., in response to receiving the service request) a verificationrequest to user device 105 to provide a verification that the unit hasdirect access (e.g., via a door, a window, and/or the like) to anexterior of the multi-unit building. User device 105 may provide, inresponse to the verification request, a verification response indicatingwhether the unit has direct access to an exterior of the multi-unitbuilding. For example, user device 105 may cause the verificationrequest to be displayed on a display screen of user device 105, and theuser of user device 105 may interact with the input interface of userdevice 105 to cause user device 105 to generate and send theverification response to service qualification platform 110.

When the verification response indicates that the unit does not havedirect access to an exterior of the multi-unit building, the servicequalification platform 110 may determine that the unit is not capable ofreceiving the service and may perform one or more associated actionsdescribed herein in relation to FIG. 1E and reference number 140. Whenthe verification response indicates that the unit has direct access toan exterior of the multi-unit building, the service qualificationplatform 110 may perform one or more of the processing steps describedherein in relation to FIGS. 1B-1E.

As shown in FIG. 1B and by reference number 120, service qualificationplatform 110 may obtain a service coverage mapping associated with themulti-unit building (e.g., based on the building location information,the unit identifier, the floor information, and/or the like, included inthe service request). Service qualification platform 110 may obtain theservice coverage mapping from a service coverage data structure (e.g., adatabase, a table, a list, and/or the like) associated with servicequalification platform 110 (e.g., that is included in the servicequalification platform 110 and/or accessible to the servicequalification platform 110).

The service coverage data structure may map a plurality of servicecoverage mappings to a plurality of sets of building locationinformation for a plurality of multi-unit buildings. For example, asshown in FIG. 1B, a plurality of multi-unit buildings (shown asbuildings A-X) may respectively comprise one or more floors (e.g.,multi-unit building A comprises floors 1-N, multi-unit building Bcomprises floors 1-M, and multi-unit building X comprises floors 1-L).Each floor of a multi-unit building may be associated with a coveragemapping that indicates an existence and/or strength of network coverageof a network (e.g., associated with the service) at one or moreperimeter coordinates of the multi-unit building. For example, floor 1of building A may be associated with a set of perimeter coordinates P₁(e.g., geographical coordinates of an exterior of floor 1 of multi-unitbuilding A) and a coverage mapping Ci. The coverage mapping Cl mayindicate that, as depicted by bold lines in FIG. 1B, network coverageexists for a subset of perimeter coordinates, of the set of perimetercoordinates P₁, associated with a west side of multi-unit building A anda south-east side of multi-unit building A. Accordingly, as shown inFIG. 1B, the service coverage data structure may include an entry thatindicates floor 1 of multi-unit building A is associated with coveragemapping Cl for perimeter coordinates P1 of multi-unit building A.

As further shown in FIG. 1B, each floor of a multi-unit building may beassociated with a set of perimeter coordinates, a subset of perimetercoordinates (e.g., that is associated with an existence and/or astrength of network coverage), and/or a coverage mapping that isdifferent than for another floor of the multi-unit building. Forexample, as shown in FIG. 1B, floor 1 of multi-unit building B isassociated with a first set of perimeter coordinates (e.g., geographicalcoordinates of an exterior of floor 1 of multi-unit building B), asubset of perimeter coordinates of the first set of perimetercoordinates (e.g., associated with a south side and an east side offloor 1 of multi-unit building B), and a first coverage mapping that isdifferent than an M^(th) set of perimeter coordinates, a subset ofperimeter coordinates of the M^(th) set of perimeter coordinates (e.g.,associated with a west side and an east side of floor M of multi-unitbuilding B), and an M^(th) coverage mapping associated with floor M ofmulti-unit building B. Accordingly, the service coverage data structuremay include a mapping to a different set of perimeter coordinates and adifferent coverage mapping for each floor of a multi-unit building.

In some implementations, to obtain the service coverage mapping from theservice coverage data structure, service qualification platform 110 mayperform, based on the building location information, the unitidentifier, the floor information, and/or the like, included in theservice request, a lookup operation of the service coverage datastructure to identify and/or select the service coverage mapping.

As shown in FIG. 1C and by reference number 125, service qualificationplatform 110 may provide a unit location request to user device 105. Theunit location request may be for an indication of a location of the unitwithin the multi-unit building. Service qualification platform 110 mayprovide the unit location request to user device 105 via a userinterface that is associated with a geographic information system (e.g.,a geographic information system that provides interactive virtual maps,interactive annotated satellite images, and/or the like). In someimplementations, the user interface may be embedded within anapplication interface of an application (e.g., an application associatedwith the geographic information system for displaying and/or depictinginteractive virtual maps, interactive annotated satellite images, and/orthe like).

In some implementations, the unit location request may identify, via theuser interface, the multi-unit building. For example, the servicequalification platform 110 may obtain, using the geographicalinformation system (e.g., based on the building location information,the unit identifier, the floor information, and/or the like, included inthe service request), an image (e.g., a satellite image) of themulti-unit building, and may cause the image of the multi-unit buildingto be depicted via the user interface. As shown in FIG. 1C, a birds-eyeview of building A is depicted via the user interface. Additionally, oralternatively, the unit location request may identify, via the userinterface, a moveable indicator for indicating a location of the unitwithin the multi-unit building. For example, as shown in FIG. 1C, theservice qualification platform 110 may cause to be displayed, via theuser interface, a request to position a unit location pin in the imageof multi-unit building A that indicates where a unit is located withinbuilding A.

In some implementations, the user of user device 105 may interact withthe user interface to select where the unit is located in the image ofthe multi-unit building. For example, the user may select a pixellocation of the image of the multi-unit building that is depicted by thegraphical user interface (e.g., by placing a unit location pin, amarker, and/or the like at the pixel location of the image).Accordingly, user device 105 may generate unit location information thatidentifies the selected pixel location of the image of the multi-unitbuilding that is associated with the unit.

As shown in FIG. 1D and by reference number 130, user device 105 mayprovide, to service qualification platform 110, the unit locationinformation via the global information system (e.g., in response toservice qualification platform 110 providing the unit location requestto user device 105). In some implementations, service qualificationplatform 110 may determine geographical coordinates associated with theunit by converting, using the geographical information system, theselected pixel location to geographical coordinates.

As shown in FIG. 1E and by reference number 135, service qualificationplatform 110 may determine a service qualification metric (e.g., basedon the building location information, the unit identifier, the floorinformation, and/or the like, included in the service request; theservice coverage mapping, the unit location information, thegeographical coordinates associated with the unit, and/or the like). Theservice qualification metric may indicate a capability of receiving theservice within the unit. For example, the service qualification metricmay indicate whether the unit is associated with one or more perimetercoordinates of the multi-unit building where network coverage existsand/or where the network coverage is sufficiently strong to allow theservice to be provided to the unit.

In some implementations, service qualification platform 110 mayidentify, from the service coverage mapping, perimeter coordinates ofthe multi-unit building (e.g., sets of geographical coordinates of aperimeter of the multi-unit building that are associated with networkcoverage). Service qualification platform 110 may determine, based onthe perimeter coordinates, the unit location information, thegeographical coordinates associated with the unit, and/or the like, aperimeter location of the multi-unit building that is nearest to theunit, and may determine a service coverage metric at the perimeterlocation. The service coverage metric may indicate whether the unit iswithin a threshold distance of the perimeter location (e.g., to allowthe network coverage to reach the unit). The service qualificationplatform 110 may determine the service qualification metric based on theservice coverage metric. For example, the service qualification metricmay indicate that the unit is capable of receiving the service when theservice coverage metric indicates that the unit is within the thresholddistance of the perimeter location. As another example, the servicequalification metric may indicate that the unit is not capable ofreceiving the service when the service coverage metric indicates thatthe unit is not within the threshold distance of the perimeter location.Additional details regarding determining the service qualificationmetric are described herein in relation to FIGS. 2A-2B.

In some implementations, when the service coverage metric indicates thatthe unit is not capable of receiving the service, the servicequalification platform 110 may determine, based on the perimetercoordinates, the unit location information, the geographical coordinatesassociated with the unit, and/or the like, an additional perimeterlocation of the multi-unit building that is next nearest (e.g., afterthe perimeter location) to the unit and may determine an additionalservice coverage metric at the additional perimeter location. Theadditional service coverage metric may indicate whether the unit iswithin the threshold distance of the additional perimeter location(e.g., to allow the network coverage to reach the unit). The servicequalification platform 110 may determine an additional servicequalification metric based on the additional service coverage metric.The service qualification platform 110 may continue to performiterations of determining new perimeter locations, new service coveragemetrics, and/or new service qualification metrics in this way until aservice coverage metric indicating that the unit is capable of receivingthe service is found, or until a threshold number of iterations havebeen attempted.

As further shown in FIG. 1E and by reference number 140, servicequalification platform 110 may perform one or more actions based on theservice qualification metric. In some implementations, the one or moreactions may include providing, to user device 105, a notificationindicating whether the unit is qualified for service. For example,service qualification platform 110 may qualify the unit for the service(e.g., by updating one or more records to indicate that the unit hasbeen qualified) based on the service qualification metric indicatingthat the unit is capable of receiving the service (e.g., when theservice qualification metric satisfies a threshold for providing theservice). The service qualification platform 110 may therefore provide,to user device 105, a notification indicating that the unit is qualifiedfor the service. As another example, service qualification platform 110may determine that the service qualification metric indicates that theunit is not capable of receiving the service (e.g., when the servicequalification metric does not satisfy the threshold for providing theservice) and may provide a notification indicating that the unit is notqualified for the service.

In some implementations, the one or more actions may include updating aservice coverage model. For example, service qualification platform 110may update (or cause to be updated) a service coverage model associatedwith the service coverage mapping to include the unit identifier, theunit location information, the geographical coordinates associated withthe unit, and/or the like. The service coverage model may be trained toidentify unit locations within multi-unit buildings based on historicaldata associated with identifying other units within other multi-unitbuildings. In some implementations, the service coverage model may beused to update one or more entries in the service coverage datastructure.

In some implementations, the one or more actions may include causing amodification to a network associated with the service. For example, whenthe service qualification metric does not satisfy the threshold forproviding the service, service qualification platform 110 may cause amodification to a network configured to provide the service (e.g., tocause network coverage to reach a perimeter location of the multi-unitbuilding that is nearest to the unit).

In some implementations, the one or more actions may include providing anotification to a service representative that indicates whether the unitis qualified for the service. For example, service qualificationplatform 110 may provide, to a user device of the servicerepresentative, a notification indicating that the unit is qualified forthe service, to allow the service representative to communicate with theuser of user device 105 to sign up for the service. As another example,service qualification platform 110 may provide, to the user device ofthe service representative, a notification indicating that the unit isnot qualified for the service, to allow the service representative tocommunicate with the user of user device 105 to sign up for a differentservice (e.g., establishment of a local area network via a wirednetwork)

As indicated above, FIGS. 1A-1E are provided merely as one or moreexamples. Other examples may differ from what is described with regardto FIGS. 1A-1E. The number and arrangement of devices shown in FIGS.1A-1E are provided as an example. In practice, there may be additionaldevices, fewer devices, different devices, or differently arrangeddevices than those shown in FIGS. 1A-1E. Furthermore, two or moredevices shown in FIGS. 1A-1E may be implemented within a single device,or a single device shown in FIGS. 1A-1E may be implemented as multiple,distributed devices. Additionally, or alternatively, a set of devices(e.g., one or more devices) shown in FIGS. 1A-1E may perform one or morefunctions described as being performed by another set of devices shownin FIGS. 1A-1E.

FIGS. 2A-2B are diagrams of one or more example implementations 200related to determining a service qualification metric described herein.As shown in FIG. 2A and reference number 210, a user of user device 105may interact with a user interface provided by a geographicalinformation system to indicate a location of a unit within a multi-unitbuilding by placing a unit location pin at a pixel location of an imageof the multi-unit building. User device 105 may send unit locationinformation identifying the indicated location of the unit to servicequalification platform 110.

In some implementations, service qualification platform 110 mayidentify, based on a service coverage mapping associated with the unitand/or the multi-unit building, perimeter coordinates of the multi-unitbuilding (e.g., that are associated with network coverage). As shown inFIG. 2B and by reference number 220, service qualification platform 110may identify, based on the perimeter coordinates and the unit locationinformation, a nearest perimeter location, to the unit, of themulti-unit building.

In some implementations, service qualification platform 110 maydetermine whether a location of the unit (e.g., indicated by the unitlocation information) is within a threshold distance of the perimeterlocation. For example, service qualification platform 110 may determinewhether the location of the unit is within a three meter radius of theperimeter location. The service qualification platform 110 may generatea service coverage metric to indicate whether the location of the unitis within the threshold distance of the perimeter location.Additionally, or alternatively, service qualification platform 110 maygenerate the service coverage metric to indicate a distance between thelocation of the unit and the perimeter location.

As shown by reference number 230, service qualification platform 110 maydetermine a service qualification metric based on the service coveragemetric. For example, the service coverage metric may indicate, when theservice coverage metric indicates that the unit is within the thresholddistance of the perimeter location, that the unit is capable ofreceiving the service. In some implementations, the service coveragemetric may indicate a potential strength of network coverage of anetwork associated with the service (e.g., based on the distance betweenthe location of the unit and the perimeter location). As anotherexample, the service coverage metric may indicate that the unit is notcapable of receiving the service when the service coverage metricindicates that the unit is not within the threshold distance of theperimeter location.

As indicated above, FIGS. 2A-2B are provided as an example. Otherexamples may differ from what is described with regard to FIGS. 2A-2B.The number and arrangement of devices shown in FIGS. 2A-2B are providedas an example. In practice, there may be additional devices, fewerdevices, different devices, or differently arranged devices than thoseshown in FIGS. 2A-2B. Furthermore, two or more devices shown in FIGS.2A-2B may be implemented within a single device, or a single deviceshown in FIGS. 2A-2B may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) shown in FIGS. 2A-2B may perform one or more functionsdescribed as being performed by another set of devices shown in FIGS.2A-2B.

FIG. 3 is a diagram of an example environment 300 in which systemsand/or methods described herein may be implemented. As shown in FIG. 3,environment 300 may include service qualification platform 110. Theservice qualification platform 110 may include one or more elements of acloud computing system 302 and/or may execute within the cloud computingsystem 302 (e.g., as one or more virtual computing systems 306). Thecloud computing system 302 may include one or more elements 303-317, asdescribed in more detail below. As further shown in FIG. 3, environment300 may include a network 320, and/or user device 105. Devices ofenvironment 300 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

The cloud computing system 302 includes computing hardware 303, aresource management component 304, a host operating system (OS) 305,and/or one or more virtual computing systems 306. The resourcemanagement component 304 may perform virtualization (e.g., abstraction)of computing hardware 303 to create the one or more virtual computingsystems 306. Using such virtualization, the resource managementcomponent 304 enables a single computing device (e.g., a computer, aserver, a host device, and/or the like) to operate as if the singlecomputing device were multiple computing devices, such as by creatingmultiple isolated virtual computing systems 306 from computing hardware303 of the single computing device. The multiple virtual computingsystems 306 operate independently from one another and do not interactwith one another. In this way, computing hardware 303 can operate moreefficiently, with lower power consumption, higher reliability, higheravailability, higher utilization, greater flexibility, and lower costthan using separate computing devices.

Computing hardware 303 includes hardware and corresponding resourcesfrom one or more computing devices. For example, computing hardware 303may include hardware from a single computing device (e.g., a singleserver or host device) or from multiple computing devices (e.g.,multiple servers or host devices), such as multiple computing devices inone or more data centers, server farms, server pools, and/or the like.As shown, computing hardware 303 may include one or more processors 307,one or more memories 308, one or more storage components 309, and/or oneor more networking components 310. Computing hardware 303 may beinterconnected via one or more wired and/or wireless buses, which mayinterconnect computing hardware 303 within a single computing deviceand/or across multiple computing devices.

A processor 307 includes a central processing unit, a graphicsprocessing unit, and/or the like. A memory 308 includes random-accessmemory, read-only memory, and/or the like. The memory 308 may store aset of instructions (e.g., one or more instructions) for execution bythe processor 307. The processor 307 may execute the set of instructionsto perform one or more operations or processes described herein. In someimplementations, execution of the set of instructions, by one or moreprocessors 307, causes the one or more processors 307 and/or the servicequalification platform 110 to perform one or more operations orprocesses described herein. A storage component 309 includes a hard diskor another type of storage device that stores information, data, and/orsoftware (e.g., code, instructions, and/or the like) related to theoperation and use of the service qualification platform 110. In someimplementations, memory 308 and/or storage component 309 is/areimplemented as a non-transitory computer readable medium. A networkingcomponent 310 includes a network interface and corresponding hardwarethat enables the service qualification platform 110 to communicate withother devices of environment 300 via a wired connection and/or awireless connection, such as via network 320. Additional examples of aprocessor, a memory, a storage component, and a networking component(e.g., a communication interface) are described elsewhere herein.

The resource management component 304 includes a virtualizationapplication (e.g., executing on hardware, such as computing hardware303) capable of virtualizing computing hardware 303 to start (e.g.,create or spin up), stop (e.g., delete or tear down), and/or manage oneor more virtual computing systems 306. Such virtualization may includeoperating system virtualization, shared kernel virtualization (e.g.,container-based virtualization), kernel level virtualization, hypervisorvirtualization, paravirtualization, full virtualization, hardwarevirtualization, and/or the like. The resource management component 304may control access to and/or use of computing hardware 303 and/orsoftware executing on computing hardware 303. Additionally, oralternatively, the resource management component 304 may perform binaryrewriting to scan instructions received from a virtual computing system306 and replace any privileged instructions with safe emulations ofthose instructions. The resource management component 304 may include ahypervisor or a virtual machine monitor, such as when the virtualcomputing systems 306 are virtual machines 311. Additionally, oralternatively, the resource management component 304 may include acontainer manager, such as when the virtual computing systems 306 arecontainers 312.

In some implementations, the resource management component 304 executeswithin and/or in coordination with a host operating system 305. Forexample, the resource management component 304 may execute on top of thehost operating system 305 rather than interacting directly withcomputing hardware 303, such as when the resource management component304 is a hosted hypervisor (e.g., a Type 2 hypervisor) or a containermanager. In this case, the host operating system 305 may control accessto and/or use of computing hardware 303 and/or software executing oncomputing hardware 303 based on information and/or instructions receivedfrom the resource management component 304. Alternatively, the resourcemanagement component 304 may interact directly with computing hardware303 rather than interacting with the host operating system 305, such aswhen the resource management component 304 is a bare-metal hypervisor(e.g., a Type 1 hypervisor). Thus, in some implementations, the cloudcomputing system 302 does not include a host operating system 305. Insome implementations, the host operating system 305 includes and/orexecutes an administrator application to enable a system administratorto manage, customize, and/or configure cloud computing system 302.

A virtual computing system 306 includes a virtual environment thatenables cloud-based execution of operations and/or processes describedherein using computing hardware 303. As shown, a virtual computingsystem 306 may include a virtual machine 311, a container 312, a hybridenvironment 313 that includes a virtual machine and a container, and/orthe like. A virtual computing system 306 may execute one or moreapplications 314 using a file system 315. The file system 315 mayinclude binary files, software libraries, and/or other resourcesrequired to execute applications 314 on a guest operating system 316 orthe host operating system 305. In some implementations, a virtualcomputing system 306 (e.g., a virtual machine 311 or a hybridenvironment 313) includes a guest operating system 316. In someimplementations, a virtual computing system 306 (e.g., a container 312or a hybrid environment 313) includes a container manager 317.

A virtual machine 311 is an emulation of a computing device that enablesexecution of separate, isolated instances of virtual computing devices(e.g., multiple virtual machines 311) on the same computing hardware303. The guest operating systems 316 and applications 314 of multiplevirtual machines 311 may share computing hardware 303 from a singlecomputing device or from multiple computing devices (e.g., a pool ofcomputing devices). Each separate virtual machine 311 may include aguest operating system 316, a file system 315, and one or moreapplications 314. With a virtual machine 311, the underlying computinghardware 303 is virtualized, and the guest operating system 316 executeson top of this virtualized hardware. Using virtual machines 311 enablesdifferent types of guest operating systems 316 to execute on the samecomputing hardware 303 in an isolated environment, but with moreresource usage and overhead than containers 312.

Unlike a virtual machine 311, a container 312 virtualizes a hostoperating system 305 rather than the underlying computing hardware 303.Thus, a container 312 does not require a guest operating system 316because the application(s) 314 included in the container 312 executedirectly on the host operating system 305 using a file system 315included in the container 312. Each separate container 312 may share thekernel of the host operating system 305, and different applications 314within a single container 312 may share a file system 315. This sharingof a file system 315 among multiple applications 314 reduces the need toreproduce operating system code for different applications, and enablesa single host operating system 305 to execute multiple applications 314and/or containers 312. As a result, containers 312 enable a greaterquantity of applications 314 to execute on a smaller quantity ofcomputing devices as compared to virtual machines 311.

A hybrid environment 313 includes elements of a virtual machine 311 anda container 312. For example, a hybrid environment 313 may include aguest operating system 316 that executes on top of virtualized hardware.A container manager 317 may execute on top of the guest operating system316 to start, stop, and/or manage one or more containers within thehybrid environment 313. Using a hybrid environment 313 enables differenttypes of guest operating systems 316 to execute on the same computinghardware 303 in an isolated environment, while also enabling lightweightcontainers to execute on top of the guest operating system 316.

The quantity of applications 314 shown in FIG. 3 as executing withineach virtual computing system 306 is shown as an example, and adifferent quantity of applications 314 may execute within each virtualcomputing system. Furthermore, although the service qualificationplatform 110 may include one or more elements 303-317 of the cloudcomputing system 302, may execute within the cloud computing system 302,and/or may be hosted within the cloud computing system 302, in someimplementations, the service qualification platform 110 may not becloud-based (e.g., may be implemented outside of a cloud computingsystem) or may be partially cloud-based. For example, the servicequalification platform 110 may include one or more devices that are notpart of the cloud computing system 302, such as device 400 of FIG. 4,which may include a standalone server or another type of computingdevice. The service qualification platform 110 may perform one or moreoperations and/or processes described in more detail elsewhere herein.

Network 320 includes one or more wired and/or wireless networks. Forexample, network 320 may include a cellular network (e.g., a fifthgeneration (5G) network, a fourth generation (4G) network, a long-termevolution (LTE) network, a third generation (3G) network, a codedivision multiple access (CDMA) network, etc.), a public land mobilenetwork (PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, and/orthe like, and/or a combination of these or other types of networks. Thenetwork 320 enables communication among the devices of environment 300.

User device 105 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information, such asinformation described herein. For example, user device 105 may include amobile phone (e.g., a smart phone, a radiotelephone, and/or the like), alaptop computer, a tablet computer, a desktop computer, a handheldcomputer, a gaming device, a wearable communication device (e.g., asmart watch, a pair of smart glasses, a heart rate monitor, a fitnesstracker, smart clothing, smart jewelry, a head mounted display, and/orthe like) or a similar type of device. User device 105 may communicatewith one or more other devices of environment 300, as describedelsewhere herein.

The number and arrangement of devices and networks shown in FIG. 3 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 3. Furthermore, two or more devices shown in FIG. 3 may beimplemented within a single device, or a single device shown in FIG. 3may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 300 may perform one or more functions described as beingperformed by another set of devices of environment 300.

FIG. 4 is a diagram of example components of a device 400. Device 400may correspond to user device 105, service qualification platform 110,and/or computing hardware 303. In some implementations, user device 105,service qualification platform 110, and/or computing hardware 303 mayinclude one or more devices 400 and/or one or more components of device400. As shown in FIG. 4, device 400 may include a bus 410, a processor420, a memory 430, a storage component 440, an input component 450, anoutput component 460, and a communication interface 470.

Bus 410 includes a component that permits communication among thecomponents of device 400. Processor 420 is implemented in hardware,firmware, or a combination of hardware and software. Processor 420 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 420includes one or more processors capable of being programmed to perform afunction. Memory 430 includes a random-access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 420.

Storage component 440 stores information and/or software related to theoperation and use of device 400. For example, storage component 440 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 450 includes a component that permits device 400 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 450 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 460 includes a component that providesoutput information from device 400 (e.g., a display, a speaker, and/orone or more LEDs).

Communication interface 470 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 400 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 470 may permit device 400to receive information from another device and/or provide information toanother device. For example, communication interface 470 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, an RF interface, a universal serial bus (USB)interface, a wireless local area interface, a cellular networkinterface, and/or the like.

Device 400 may perform one or more processes described herein. Device400 may perform these processes based on processor 420 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 430 and/or storage component 440. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 430 and/or storagecomponent 440 from another computer-readable medium or from anotherdevice via communication interface 470. When executed, softwareinstructions stored in memory 430 and/or storage component 440 may causeprocessor 420 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 4 are provided asan example. In practice, device 400 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 4. Additionally, or alternatively, aset of components (e.g., one or more components) of device 400 mayperform one or more functions described as being performed by anotherset of components of device 400.

FIG. 5 is a flow chart of an example process 500 associated withidentifying a service qualification of a unit in a multi-unit building.In some implementations, one or more process blocks of FIG. 5 may beperformed by a device (e.g., service qualification platform 110). Insome implementations, one or more process blocks of FIG. 5 may beperformed by another device or a group of devices separate from orincluding the device, such as user device 105. Additionally, oralternatively, one or more process blocks of FIG. 5 may be performed byone or more components of computing hardware 303, such as processors307, memory 308, storage component 309, networking components 310,and/or the like, and/or by one or more components of a device 400, suchas processor 420, memory 430, storage component 440, input component450, output component 460, communication interface 470, and/or the like.

As shown in FIG. 5, process 500 may include receiving a service requestto qualify a unit of a multi-unit building to receive a service (block510). For example, the device may receive (e.g., from a user device) aservice request to qualify a unit of a multi-unit building to receive aservice, as described above. In some implementations, the servicerequest includes building location information of the multi-unitbuilding and/or a unit identifier. The building location information maycomprise a street address of the multi-unit building or geographicalcoordinates of the user device. The service may comprise establishing,for a user of the unit, a local area network via an ultrawide bandwireless network.

As further shown in FIG. 5, process 500 may include obtaining a servicecoverage mapping associated with the multi-unit building (block 520).For example, the device may obtain a service coverage mapping associatedwith the multi-unit building (e.g., based on the building locationinformation and/or the unit identifier), as described above.

In some implementations, obtaining the service coverage mappingcomprises performing a lookup operation of a service coverage datastructure, where the service coverage data structure maps a plurality ofservice coverage mappings to a plurality of sets of building locationinformation for a plurality of multi-unit buildings, and selecting,based on the building location information, the service coverage mappingfrom the plurality of service coverage mappings. Additionally, oralternatively, obtaining the service coverage mapping includesdetermining, based on the service request, a floor of the unit andobtaining the service coverage mapping based on the building locationinformation and the floor.

In some implementations, prior to obtaining the service coveragemapping, process 500 includes requesting the user device to provide averification that the unit has direct access to an exterior of themulti-unit building, wherein the service coverage mapping is obtainedbased on receiving the verification, and wherein the indication of thelocation of the unit corresponds to an indication of a location of thedirect access to the exterior of the multi-unit building.

In some implementations, process 500 further includes determining, basedon the unit identifier, a floor of the multi-unit building that includesthe unit, and obtaining the service coverage mapping includes selecting,based on the floor, the service coverage mapping from a service coveragedata structure that includes a plurality of service coverage mappingsassociated with the multi-unit building.

As further shown in FIG. 5, process 500 may include providing a unitlocation request for an indication of a location of the unit within themulti-unit building (block 530). For example, the device may provide(e.g., to the user device) a unit location request for an indication ofa location of the unit within the multi-unit building, as describedabove. In some implementations, the unit location request is providedvia a user interface that is associated with a geographic informationsystem (e.g., the user interface includes a graphical interface that isassociated with the geographical information system), and the unitlocation request identifies, via the user interface, the multi-unitbuilding based on the building location information.

In some implementations, the user interface comprises a graphical userinterface, of the geographic information system, that is embedded withinan application interface of an application, and providing the unitlocation request comprises obtaining, based on the geographicalinformation system and the building location information, an image ofthe multi-unit building; depicting, via the graphical user interface,the image of the multi-unit building; and displaying a request for anindication identifying the unit located in the image, wherein the unitlocation information is received based on the graphical user interfacereceiving the indication.

In some implementations, prior to providing the unit location request,process 500 includes determining, based on the unit identifier, that theservice coverage mapping does not indicate historical servicequalification information for the unit, wherein the indication of thelocation of the unit is requested based on the service coverage mappingnot including the historical service qualification information for theunit.

As further shown in FIG. 5, process 500 may include receiving unitlocation information that is associated with the indication (block 540).For example, the device may receive (e.g., in association with the unitlocation request) unit location information that is associated with theindication, as described above. In some implementations, the userinterface comprises a graphical user interface, of the geographicalinformation system, that is embedded within an application interface ofan application, and receiving the unit location information comprisesreceiving a selected pixel location of an image that is depicted by thegraphical user interface, and converting, using the geographicalinformation system, the selected pixel location to geographicalcoordinates of the unit.

In some implementations, receiving the unit location informationincludes receiving, based on providing a request for an indication of alocation of the unit, a selected pixel location of a graphical userinterface of a geographical information system; and converting, usingthe geographical information system, the selected pixel location togeographical coordinates of the unit, wherein the geographicalcoordinates of the unit correspond to the unit location of the unitlocation information.

As further shown in FIG. 5, process 500 may include determining aservice qualification metric (block 550). For example, the device maydetermine a service qualification metric based on the service coveragemapping, the unit location information, and/or the geographicalcoordinates of the unit, as described above. In some implementations,the service qualification metric is associated with a capability ofreceiving the service within the unit, associated with qualifying theunit to enable use of the service, and/or the like.

In some implementations, determining the service qualification metriccomprises identifying, from the service coverage mapping, perimetercoordinates of the multi-unit building, wherein the perimetercoordinates comprise sets of geographical coordinates of a perimeter ofthe multi-unit building; determining, based on the perimeter coordinatesand/or the unit location information, a perimeter location that isnearest the unit; determining a service coverage metric at the perimeterlocation; and determining the service qualification metric based on theservice coverage metric. The perimeter location may be associated withnetwork coverage of a network associated with the service.

In some implementations, determining the service qualification metricincludes identifying, from the service coverage mapping and based on thegeographical coordinates, a nearest qualified location that is on aperimeter of the multi-unit building, wherein the nearest qualifiedlocation corresponds to a location on the perimeter that has beenqualified in association with the service; and determining the servicequalification metric based on a distance between the geographicalcoordinates of the unit and geographical coordinates of the nearestqualified location.

In some implementations, the perimeter location is a first perimeterlocation and the service coverage metric is a first service coveragemetric, and determining the service qualification metric includesdetermining that the service is not available at the perimeter location;determining, based on the service not being available, a second servicecoverage metric of a second perimeter location, wherein the secondperimeter location is within a threshold distance of the first perimeterlocation, and determining the service qualification metric based on thefirst service coverage metric and the second service coverage metric.

As further shown in FIG. 5, process 500 may include performing an actionassociated with the service qualification metric (block 560). Forexample, the device may perform an action associated with the servicequalification metric, as described above. In some implementations,performing the action comprises qualifying the unit for the servicebased on the service qualification metric satisfying a threshold forproviding the service, and providing, to the user device, a notificationthat the unit is qualified for the service.

In some implementations, performing the action comprises qualifying theunit for the service based on the service qualification metricsatisfying a threshold for providing the service, and updating a servicecoverage model associated with the service coverage mapping to includethe unit location information and a unit identifier of the unit, wherethe service coverage model is trained to identify unit locations withinmulti-unit buildings based on historical data associated withidentifying other units within other multi-unit buildings.

In some implementations, process 500 further includes determining thatthe service qualification metric does not satisfy a threshold forproviding the service to the unit, wherein performing the action, basedon the service metric not satisfying the threshold, includes indicating,to the user device, that the unit is not qualified for the service,causing a modification to a network that is configured to provide theservice, or updating a service coverage model that is associated withthe service coverage mapping to include the unit identifier inassociation with the geographical coordinates of the unit.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc., depending on the context.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, and/or thelike. A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: receiving, by a device andfrom a user device, a service request to qualify a unit of a multi-unitbuilding to receive a service, wherein the service request includesbuilding location information of the multi-unit building; obtaining, bythe device and based on the building location information, a servicecoverage mapping associated with the multi-unit building; providing, bythe device and to the user device, a unit location request for anindication of a location of the unit within the multi-unit building,wherein the unit location request is provided via a user interface thatis associated with a geographic information system, and wherein the unitlocation request identifies, via the user interface, the multi-unitbuilding based on the building location information; receiving, by thedevice and in association with the unit location request, unit locationinformation that is associated with the indication; determining, by thedevice, a service qualification metric based on the service coveragemapping and the unit location information, wherein the servicequalification metric is associated with a capability of receiving theservice within the unit; and performing, by the device, an actionassociated with the service qualification metric.
 2. The method of claim1, wherein the user interface comprises a graphical user interface, ofthe geographic information system, that is embedded within anapplication interface of an application, and wherein providing the unitlocation request comprises: obtaining, based on the geographicalinformation system and the building location information, an image ofthe multi-unit building; depicting, via the graphical user interface,the image of the multi-unit building; and displaying a request for anindication identifying where the unit is located in the image, whereinthe unit location information is received based on the graphical userinterface receiving the indication.
 3. The method of claim 1, whereinthe user interface comprises a graphical user interface, of thegeographical information system, that is embedded within an applicationinterface of an application, and wherein receiving the unit locationinformation comprises: receiving a selected pixel location of an imagethat is depicted by the graphical user interface; and converting, basedon the geographical information system, the selected pixel location togeographical coordinates, wherein the unit location informationcomprises the geographical coordinates.
 4. The method of claim 1,wherein obtaining the service coverage mapping comprises: performing alookup operation of a service coverage data structure, wherein theservice coverage data structure maps a plurality of service coveragemappings to a plurality of sets of building location information for aplurality of multi-unit buildings; and selecting, based on the buildinglocation information, the service coverage mapping from the plurality ofservice coverage mappings.
 5. The method of claim 1, wherein determiningthe service qualification metric comprises: identifying, from theservice coverage mapping, perimeter coordinates of the multi-unitbuilding, wherein the perimeter coordinates comprise sets ofgeographical coordinates of a perimeter of the multi-unit building;determining, based on the perimeter coordinates and the unit locationinformation, a perimeter location that is nearest the unit; determininga service coverage metric at the perimeter location; and determining theservice qualification metric based on the service coverage metric. 6.The method of claim 5, wherein the service coverage metric indicateswhether the unit is within a threshold distance of the perimeterlocation.
 7. The method of claim 1, wherein performing the actioncomprises: qualifying the unit for the service based on the servicequalification metric satisfying a threshold for providing the service;and providing, to the user device, a notification that the unit isqualified for the service, or updating a service coverage modelassociated with the service coverage mapping to include the unitlocation information and a unit identifier of the unit, wherein theservice coverage model is trained to identify unit locations withinmulti-unit buildings based on historical data associated withidentifying other units within other multi-unit buildings.
 8. A device,comprising: one or more memories; and one or more processors configuredto: receive a service request to qualify a unit of a multi-unit buildingto receive a service, wherein the service request includes buildinglocation information of the multi-unit building and a unit identifier;obtain, based on the building location information and the unitidentifier, a service coverage mapping associated with the multi-unitbuilding; request a user device, that provided the service request, toprovide, via a user interface, an indication of a location of the unitwithin the multi-unit building, wherein the user interface includes agraphical user interface that is associated with a geographicalinformation system, and wherein the indication is requested inassociation with an image of the multi-unit building being depicted viathe graphical user interface; receive, from the user device, a selectedpixel location of the user interface that corresponds to the indication;convert, using the geographical information system, the selected pixellocation to geographical coordinates of the unit; determine a servicequalification metric based on the service coverage mapping and thegeographical coordinates of the unit; and perform an action associatedwith the service qualification metric.
 9. The device of claim 8, whereinthe building location information comprises least one of: a streetaddress of the multi-unit building, or geographical coordinates of theuser device.
 10. The device of claim 8, wherein prior to obtaining theservice coverage mapping, the one or more processors are furtherconfigured to: request the user device to provide a verification thatthe unit has direct access to an exterior of the multi-unit building,wherein the service coverage mapping is obtained based on receiving theverification, and wherein the indication of the location of the unitcorresponds to an indication of a location of the direct access to theexterior of the multi-unit building.
 11. The device of claim 8, wherein,prior to requesting the indication of the location of the unit, the oneor more processors are further configured to: determine, based on theunit identifier, that the service coverage mapping does not indicatehistorical service qualification information for the unit, wherein theindication of the location of the unit is requested based on the servicecoverage mapping not including the historical service qualificationinformation for the unit.
 12. The device of claim 8, wherein the one ormore processors, when determining the service qualification metric, areconfigured to: identify, from the service coverage mapping and based onthe geographical coordinates, a nearest qualified location that is on aperimeter of the multi-unit building, wherein the nearest qualifiedlocation corresponds to a location on the perimeter that has beenqualified in association with the service; and determine the servicequalification metric based on a distance between the geographicalcoordinates of the unit and geographical coordinates of the nearestqualified location.
 13. The device of claim 8, wherein the one or moreprocessors are further configured to: determine, based on the unitidentifier, a floor of the multi-unit building that includes the unit;and wherein the one or more processors, when obtaining the servicecoverage mapping, are configured to: select, based on the floor, theservice coverage mapping from a service coverage data structure thatincludes a plurality of service coverage mappings associated with themulti-unit building.
 14. The device of claim 8, wherein the one or moreprocessors are further configured to: determine that the servicequalification metric does not satisfy a threshold for providing theservice to the unit, wherein the one or more processors, when performingthe action, are configured to, based on the service metric notsatisfying the threshold: indicate, to the user device, that the unit isnot qualified for the service, cause a modification to a network that isconfigured to provide the service, or update a service coverage modelthat is associated with the service coverage mapping to include the unitidentifier in association with the geographical coordinates of the unit.15. A non-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors, cause the one or more processors to: receive, inassociation with a service request to qualify for a service, unitlocation information that is associated with a unit of a multi-unitbuilding; obtain, based on building location information of themulti-unit building, a service coverage mapping associated with themulti-unit building; identify, from the service coverage mapping,perimeter coordinates of the multi-unit building, wherein the perimetercoordinates comprise sets of geographical coordinates of a perimeter ofthe multi-unit building; determine, based on the perimeter coordinates,a perimeter location that is nearest to a unit location of the unitlocation information; determine a service coverage metric at theperimeter location; determine, based on the service coverage metric, aservice qualification metric for the unit, wherein the servicequalification metric is associated with qualifying the unit to enableuse of the service; and provide, based on the service qualificationmetric, a notification that identifies whether the unit is qualified toenable use of the service.
 16. The non-transitory computer-readablemedium of claim 15, wherein the one or more instructions, that cause theone or more processors to obtain the service coverage mapping, cause theone or more processors to: determine, based on the service request, afloor of the unit; and obtain the service coverage mapping based on thebuilding location information and the floor.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, that cause the one or more processors to receive the unitlocation information, cause the one or more processors to: receive,based on providing a request for an indication of a location of theunit, a selected pixel location of a graphical user interface of ageographical information system; and convert, using the geographicalinformation system, the selected pixel location to geographicalcoordinates of the unit, wherein the geographical coordinates of theunit correspond to the unit location of the unit location information.18. The non-transitory computer-readable medium of claim 15, wherein theperimeter location is associated with network coverage of a networkassociated with the service.
 19. The non-transitory computer-readablemedium of claim 15, wherein the perimeter location is a first perimeterlocation and the service coverage metric is a first service coveragemetric, and wherein the one or more instructions, that cause the one ormore processors to determine the service qualification metric, cause theone or more processors to: determine that the service is not availableat the perimeter location; determine, based on the service not beingavailable, a second service coverage metric of a second perimeterlocation, wherein the second perimeter location is within a thresholddistance of the first perimeter location; and determine the servicequalification metric based on the first service coverage metric and thesecond service coverage metric.
 20. The non-transitory computer-readablemedium of claim 15, wherein the service comprises establishing, for auser of the unit, a local area network via an ultrawide band wirelessnetwork.